- Main Page
- Information on the Institution
- General Description of the Institution
- Address of İzmir University of Economics
- Academic Authorities
- Academic Calendar
- Recognition of Prior Learning
- Recognition of Study Abroad
- List of Programs Offered
- General Admission Requirements
- General Registration Procedures
- ECTS Credit Allocation
- Grading
- Arrangements for Academic Guidance
- Internationalization
- Institutional ECTS Coordinator
- Departmental Erasmus Coordinators
- Degree Programs
- Software Engineering
- Qualification Awarded
- Level of Qualification
- Specific Admission Requirements
- Qualification Requirements and Regulations
- Recognition of Prior Learning
- Profile of the Program
- Program Outcomes
- Course & Program Outcomes Matrix
- Occupational Profiles of Graduates
- Access to Further Studies
- Program Structure
- Course Structure Diagram with Credits
- Exam Regulations & Assessment & Grading
- Graduation Requirements
- Mode of Study
- Program Director (or Equivalent)
- Evaluation Questionnaires
- Courses
- General Information For Students
- About İzmir
- Cost of Living
- Accommodation
- Meals
- Medical Facilities
- Facilities for Special Needs Students
- Career Guidance Center
- Insurance
- Financial Support for Students
- Registrar's Office
- Learning Facilities
- International Programs
- Practical Information for Exchange Students
- Language Courses
- Internships
- Sports and Leisure Facilities
- Student Associations
- Useful Phone Numbers
- Diploma Supplement
- Erasmus Policy Statement
- National Qualifications
- Bologna Commission
11111
COURSE INTRODUCTION AND APPLICATION INFORMATION
se.cs.ieu.edu.tr
| Course Name | |
| Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
|---|---|---|---|---|---|
| Fall/Spring |
| Prerequisites | None | |||||
| Course Language | ||||||
| Course Type | Elective | |||||
| Course Level | - | |||||
| Mode of Delivery | - | |||||
| Teaching Methods and Techniques of the Course | ||||||
| Course Coordinator | ||||||
| Course Lecturer(s) | ||||||
| Assistant(s) | - | |||||
| Course Objectives | |
| Learning Outcomes | The students who succeeded in this course;
|
| Course Description |
|
| Core Courses | |
| Major Area Courses | ||
| Supportive Courses | X | |
| Media and Managment Skills Courses | ||
| Transferable Skill Courses |
WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES
| Week | Subjects | Required Materials |
| 1 | Introduction | Fenton and Pfleeger, ch.1 |
| 2 | The basics of measurement | Fenton and Pfleeger, ch.2 |
| 3 | Goalbased framework for measurement | Fenton and Pfleeger, ch.3 |
| 4 | Empirical investigation | Fenton and Pfleeger, ch.4 |
| 5 | Software measurement process | ISO 15939 |
| 6 | Measuring internal product attributes: size | Fenton and Pfleeger, ch.7 |
| 7 | Functional size measurement | Kan, ch.18, Sommerville, ch.26 |
| 8 | Review | |
| 9 | Midterm exam | |
| 10 | Measuring internal product attributes | Fenton and Pfleeger, ch.8 |
| 11 | Measuring external product attributes | Fenton and Pfleeger, ch.9, ISO 9126 |
| 12 | Measuring software reliability | Fenton and Pfleeger, ch.10 |
| 13 | Object oriented software measurement | Chidamber and Kemerer |
| 14 | Object oriented software measurement | Chidamber and Kemerer |
| 15 | General Evaluation | |
| 16 | Review of the Semester |
| Course Notes/Textbooks | Fenton and Pfleeger, Software Metrics: A Rigorous Practical Approach, 2nd ed., PWS Publishing Company, 1998. |
| Suggested Readings/Materials | Imagix 4D is an industry standard tool for source code analysis,static code analysis, software metrics and documentation. Kan S., Metrics and Models in Software Quality Engineering, , 2nd ed, AddisonWesley, 2003.ISO/IEC 15939: 2007. System and Software EngineeringMeasurement Process, International Organization for Standardization, 2007.ISO/IEC 91261: Software Engineering – Product Quality – Part 1: Quality model, International Organization for Standardization, 1999.Guide to the Software Engineering Body of Knowledge: 2004 ed., Abran and Moore, IEEE, April 2005.Sommerville, Software Engineering, 8e, AddisonWesley, 2007.The Common Software Measurement International Consortium, http://www.cosmicon.com/.Chidamber and Kemerer, A Metrics Suite for Object Oriented Design, IEEE Transactions on Software Engineering, Vol. 20, No. 6, June 1994. |
EVALUATION SYSTEM
| Semester Activities | Number | Weigthing |
| Participation | ||
| Laboratory / Application | ||
| Field Work | ||
| Quizzes / Studio Critiques | - | - |
| Portfolio | ||
| Homework / Assignments | ||
| Presentation / Jury | ||
| Project | 15 | |
| Seminar / Workshop | ||
| Oral Exam | ||
| Midterm | 1 | 35 |
| Final Exam | 1 | 50 |
| Total |
| Weighting of Semester Activities on the Final Grade | 1 | 50 |
| Weighting of End-of-Semester Activities on the Final Grade | 1 | 50 |
| Total |
ECTS / WORKLOAD TABLE
| Semester Activities | Number | Duration (Hours) | Workload |
|---|---|---|---|
| Course Hours (Including exam week: 16 x total hours) | 16 | 2 | 32 |
| Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
| Study Hours Out of Class | 16 | 1 | |
| Field Work | |||
| Quizzes / Studio Critiques | 2 | 5 | |
| Portfolio | |||
| Homework / Assignments | |||
| Presentation / Jury | |||
| Project | |||
| Seminar / Workshop | |||
| Oral Exam | |||
| Midterms | 1 | 9 | |
| Final Exams | 1 | 23 | |
| Total | 90 |
COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP
| # | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
| 1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
| 2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
| 3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
| 4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
| 5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | X | ||||
| 6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | X | ||||
| 7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | X | ||||
| 8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | X | ||||
| 9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
| 10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
| 11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
| 12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
| 13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest